Outlook error when sending email from shared mailbox or from a user who has full access to a mailbox.

This is the error users keep receiving when trying to send email from someone mailbox that they have full access to. They can read emails file just sending is a problem.

Error is [0x80070005-00000000-00000000]

Make sure your Outlook client is fully updated.

In general, error 0x80070005 meams the issue is related to permission issue. Try to remove and re-add the full access permission from EMC to check if you still receive the NDRs.

By the way, does it happen in specific user/mailbox or in all of mailbox. Thanks.

Tony Chen
TechNet Community Support

Happens to only specific mailboxes that had the older exchange shared mailbox mounted to their outlook and their mailboxes copied over to 2013. The work around i found was to setup those shared mailboxes first before creating their personal mailbox profile. And set their personal profile to default after the shared mailboxes were all working. No idea why this is happening, but if mount or open someones mailbox that has full access with a new user I do not run into these issues, it must be an artifact from migration of these users mailboxes and they still attempting to use old paths for exchange server for sending... there is no problem with grabbing new mails .. So it is/was a bit tricky issue but my workaround it seems to be working so far.

• Marked as answer by Tony Chen CHNMicrosoft contingent staff, Moderator Friday, June 14, 2013 1:42 AM

Happens to only specific mailboxes that had the older exchange shared mailbox mounted to their outlook and their mailboxes copied over to 2013. The work around i found was to setup those shared mailboxes first before creating their personal mailbox profile. And set their personal profile to default after the shared mailboxes were all working. No idea why this is happening, but if mount or open someones mailbox that has full access with a new user I do not run into these issues, it must be an artifact from migration of these users mailboxes and they still attempting to use old paths for exchange server for sending... there is no problem with grabbing new mails .. So it is/was a bit tricky issue but my workaround it seems to be working so far.

• Marked as answer by Tony Chen CHNMicrosoft contingent staff, Moderator Friday, June 14, 2013 1:42 AM

Happens to only specific mailboxes that had the older exchange shared mailbox mounted to their outlook and their mailboxes copied over to 2013. The work around i found was to setup those shared mailboxes first before creating their personal mailbox profile. And set their personal profile to default after the shared mailboxes were all working. No idea why this is happening, but if mount or open someones mailbox that has full access with a new user I do not run into these issues, it must be an artifact from migration of these users mailboxes and they still attempting to use old paths for exchange server for sending... there is no problem with grabbing new mails .. So it is/was a bit tricky issue but my workaround it seems to be working so far.

• Marked as answer by Tony Chen CHNMicrosoft contingent staff, Moderator Friday, June 14, 2013 1:42 AM

tony, i realized the problem is back again this week. Nothing on exchange  changed but seems like the users unable to send again. This is one weird one. Can only read the mailboxes emails but cannot send from it. It was working last week and this week after exchange reboot looks like its back. Anyone ever run into this error and how was it resolved properly ?

We have it happening after migrating from a POP email to Office365 but it only happens when trying to send to an email address that just forwards to another real email.  The alias is JCohen@ourdomain.org and the real email that JCohen forwards to is JKohn@ourdomain.org

• Proposed as answer by vdever Thursday, October 03, 2013 1:03 PM

We have it happening after migrating from a POP email to Office365 but it only happens when trying to send to an email address that just forwards to another real email.  The alias is JCohen@ourdomain.org and the real email that JCohen forwards to is JKohn@ourdomain.org

• Proposed as answer by vdever Thursday, October 03, 2013 1:03 PM

We have it happening after migrating from a POP email to Office365 but it only happens when trying to send to an email address that just forwards to another real email.  The alias is JCohen@ourdomain.org and the real email that JCohen forwards to is JKohn@ourdomain.org

• Proposed as answer by vdever Thursday, October 03, 2013 1:03 PM

Strangely enough, this only happens for one of our users from Outlook(Desktop).

We have been running in to this issue as well,  I have fixed this issue by deleting the offline address book folder and by  hitting the X on the type ahead. 

I hope this helps people. 

the path to the offline address book is  %appdata%\local\Microsoft\outlook\  make sure outlook and lync is closed and delete the offline address book folder re open outlook and try again.

Yeah, you can solve it temporarily that way. This is the only way it got solved it permanently for me though:

http://blog.groundx.se/error-0x80070005-00000000-00000000-outlook-2013/

In O365, I just had to grant the user "Send As" permissions.  Overlooked that as we assumed the "Full Access" token would cover it.

• Proposed as answer by Berserk41 Wednesday, July 09, 2014 5:55 AM
• Unproposed as answer by Berserk41 Wednesday, July 09, 2014 5:55 AM

In O365, I just had to grant the user "Send As" permissions.  Overlooked that as we assumed the "Full Access" token would cover it.

• Proposed as answer by Berserk41 Wednesday, July 09, 2014 5:55 AM
• Unproposed as answer by Berserk41 Wednesday, July 09, 2014 5:55 AM

In O365, I just had to grant the user "Send As" permissions.  Overlooked that as we assumed the "Full Access" token would cover it.

• Proposed as answer by Berserk41 Wednesday, July 09, 2014 5:55 AM
• Unproposed as answer by Berserk41 Wednesday, July 09, 2014 5:55 AM
• Proposed as answer by Protie Oy Wednesday, June 24, 2015 12:01 PM
• Unproposed as answer by Protie Oy Wednesday, June 24, 2015 12:01 PM

Happened to me on Outlook 2013 & Exchange 2013.

What worked for us was to disabled cached mode, restart outlook, enable cached mode, restart outlook.

Hopefully this will help someone.

I ran into this after migrating mailboxes to Exchange 2013.  My mailbox migrated just fine, but my second and third did not work from my Outlook.  None of the suggestions worked, including deleting and recreating one of the Exchange accounts in my Outlook.  Eventually I figured out that even though Outlook was allowing the account setup and password I was typing, it was not using them. I had Send and Full Access permission to the mailbox, from years ago before Outlook 2010 allowed multiple accounts, and Outlook was using my credentials to connect and not the password I was providing.  Setting the account's More Settings/Security/Always prompt for logon credentials option forced it to ask, then I could turn that option off again.

I had this error when moving a client from On Premise exchange to O365.

All the correct Send as permissions had been set in powershell. We had to re download the global address list and each user had to pick the address they wanted to Send As from the Global address list(rather than typing it for example). After that it worked fine and i was able to hide the distribution groups once again in the GAL so its looked tidy.

Just ran into this problem.  We solved it by also granting the users Send-as permission.  I'm not sure why Send-as trumped Full Access, though.

• Proposed as answer by ElRandyTech Friday, November 21, 2014 8:37 PM

Just ran into this problem.  We solved it by also granting the users Send-as permission.  I'm not sure why Send-as trumped Full Access, though.

• Proposed as answer by ElRandyTech Friday, November 21, 2014 8:37 PM

Just ran into this problem.  We solved it by also granting the users Send-as permission.  I'm not sure why Send-as trumped Full Access, though.

• Proposed as answer by ElRandyTech Friday, November 21, 2014 8:37 PM

Full Access grants permission to access the mailbox and the mailbox folders and is an Exchange property.

Send As permission grants AD access to send as the mailbox and is an Active Directory property.

For example examine the EMC command for granting send as access:

Add-ADPermission "Mailbox Name" -User "Domain\Username" -Extendedrights "Send As"

Source: http://technet.microsoft.com/en-us/library/bb676368(v=exchg.141).aspx

• Edited by Thorr686 Tuesday, January 13, 2015 10:27 AM
• Proposed as answer by Jiri Strachota 22 hours 44 minutes ago
• Unproposed as answer by Jiri Strachota 22 hours 44 minutes ago

Full Access grants permission to access the mailbox and the mailbox folders and is an Exchange property.

Send As permission grants AD access to send as the mailbox and is an Active Directory property.

For example examine the EMC command for granting send as access:

Add-ADPermission "Mailbox Name" -User "Domain\Username" -Extendedrights "Send As"

Source: http://technet.microsoft.com/en-us/library/bb676368(v=exchg.141).aspx

• Edited by Thorr686 Tuesday, January 13, 2015 10:27 AM
• Proposed as answer by Jiri Strachota Friday, March 27, 2015 8:44 AM
• Unproposed as answer by Jiri Strachota Friday, March 27, 2015 8:44 AM

Full Access grants permission to access the mailbox and the mailbox folders and is an Exchange property.

Send As permission grants AD access to send as the mailbox and is an Active Directory property.

For example examine the EMC command for granting send as access:

Add-ADPermission "Mailbox Name" -User "Domain\Username" -Extendedrights "Send As"

Source: http://technet.microsoft.com/en-us/library/bb676368(v=exchg.141).aspx

• Edited by Thorr686 Tuesday, January 13, 2015 10:27 AM
• Proposed as answer by Jiri Strachota Friday, March 27, 2015 8:44 AM
• Unproposed as answer by Jiri Strachota Friday, March 27, 2015 8:44 AM

Full Access grants permission to access the mailbox and the mailbox folders and is an Exchange property.

Send As permission grants AD access to send as the mailbox and is an Active Directory property.

For example examine the EMC command for granting send as access:

Add-ADPermission "Mailbox Name" -User "Domain\Username" -Extendedrights "Send As"

Source: http://technet.microsoft.com/en-us/library/bb676368(v=exchg.141).aspx

• Edited by Thorr686 Tuesday, January 13, 2015 10:27 AM
• Proposed as answer by Jiri Strachota Friday, March 27, 2015 8:44 AM
• Unproposed as answer by Jiri Strachota Friday, March 27, 2015 8:44 AM
• Proposed as answer by Indy S Thursday, July 23, 2015 5:43 PM

I had this error today, not for the first time. But this time I realized that it occurred on Resend of a message which had been originally sent via an expired MS Office365 subscription (same domain as now).

So I made a new Resend AND chose From explicitly (seemingly the same thing). The message went off OK.

If permissions are correct try removing the name from the from dropdown by pressing the X and then re-add the address.

this normally happens if the from address has changed it's alias

If permissions are correct try removing the name from the from dropdown by pressing the X and then re-add the address.

this normally happens if the from address has changed it's alias

• Proposed as answer by rod.fuller 10 hours 42 minutes ago

If permissions are correct try removing the name from the from dropdown by pressing the X and then re-add the address.

this normally happens if the from address has changed it's alias

• Proposed as answer by rod.fuller Tuesday, May 26, 2015 8:49 PM

We also resolved it by removing the Send As name and adding it back in.

I recently had this issue with a user trying to forward a contact. Tried all the remedies and nothing worked. Ended up being a corrupt contact card. After deleting and recreating the card it worked just fine.